[Silverlight] Suggestion – Move INotifyCollectionChanged from System.Windows.dll to System.dll
Posted
by Benjamin Roux
on ASP.net Weblogs
See other posts from ASP.net Weblogs
or by Benjamin Roux
Published on Wed, 19 May 2010 20:22:18 GMT
Indexed on
2010/05/19
23:31 UTC
Read the original article
Hit count: 1019
I just submitted a suggestion on Microsoft Connect to move the INotifyCollectionChanged from System.Windows.dll to System.dll.
You can review it here: https://connect.microsoft.com/VisualStudio/feedback/details/560184/move-inotifycollectionchanged-from-system-windows-dll-to-system-dll
Here’s the reason why I suggest that.
Actually I wanted to take advantages of the new feature of Silverlight/Visual Studio 2010 for sharing assemblies (see http://blogs.msdn.com/clrteam/archive/2009/12/01/sharing-silverlight-assemblies-with-net-apps.aspx). Everything went fine until I try to share a custom collection (with custom business logic) implementing INotifyCollectionChanged.
This modification has been made in the .NET Framework 4 (see https://connect.microsoft.com/VisualStudio/feedback/details/488607/move-inotifycollectionchanged-to-system-dll) so maybe it could be done in Silverlight too.
If you think this is justifiable you can vote for it.
© ASP.net Weblogs or respective owner